![]() |
|||
![]()
|
![]() |
![]() Click Here! |
![]() |
SWITCHING AND ROUTING IN THE LAN LAN switching has emerged as the most cost-effective way to segment shared LANs so that each user gets a greater share of the available bandwidth. Switching can be employed to link shared LAN segments together, or to deliver dedicated bandwidth to individual hosts, whether they be desktop PCs or server machines. Switching can also be used to link LAN technologies of different speedsfor example, connecting users with 10 Mbps Ethernet connections to a 100 Mbps Fast Ethernet uplink to the LAN backbone. The use of ATM with Ethernet or Token Ring LAN Emulation is a direct extension of the concept of LAN switching. LAN switching operates at Layer 2 of the OSI 7-layer model of networking protocols, the Data Link layer. This means that LAN switches forward packets based on their Ethernet or Token Ring destination Media Access Control (MAC) address, or, in the case of source routed Token Ring, on the Routing Information Field (RIF). LAN switches are therefore transparent to Network Layer protocols such as the Internet Protocol (IP) or Novell's Internetwork Packet eXchange (IPX). LAN switches have a number of physical ports for connection to LAN segments, typically in the range 8 to 128 or more, and they learn which ports are associated with which MAC destination addresses by extracting the source MAC address of each packet that is sent to the switch and learning the association between the MAC address and the port on which the packet was received. Because they are largely self-configuring, LAN switches are easy to install, configure and manage. Routers, by contrast, operate at Layer 3 of the 7-layer model, the Network Layer, and they forward packets according to Network Layer address prefixes in conjunction with routing tables held in router memory. These routing tables are kept up-to-date with the aid of routing protocols which are used to exchange reachability information between routers. Routers are much more complex than LAN switches, and are certainly more costly. A good deal of software is involved with the processing of each packet through a router, so they are generally much slower than LAN switches, and harder to configure and manage. LAN switches are simple, cost-effective and offer excellent performance. So when we need to increase the capacity of the LAN, why not migrate the entire LAN infrastructure to operate exclusively on LAN switches? The answer is that, in some cases, this is indeed possiblebut more often than not there is some necessity for routing in the LAN, for one or more of the following reasons:
Alternative solutions do exist for the first three of these requirements for routing functionality in the LAN. Some organizations, recognizing the value of moving to a fully switched LAN, are changing to private IP addressing schemes which provide the flexibility to assign all stations in one site to a single subnet. Where Internet access is required, an address translation gateway is employed which also operates as a security firewall. Security within the LAN can be implemented exclusively at the level of the end systemdepending on the application software or the network operating systemthereby removing the need for the network to implement access control. And the broadcast issue can be addressed by more sophisticated means than simply breaking the network up into broadcast domains. For example, some LAN switches can apply Layer 3 intelligence to the filtering of unnecessary broadcast traffic, as in Madge's Active Broadcast Control technology. Nevertheless, in many real networks the practicalities of the situation will dictate that routing functionality is required, for one or more of the reasons we have identified. And this means that if conventional LAN switches are deployed, it is necessary to deploy also routers. (See Exhibit 2-2-2.)
Further discussion on the coexistence of switching and routing in the LAN can be found in the Madge white paper The Architecture of Switched LANs, March 1996.
|
![]() |
|
Use of this site is subject certain Terms & Conditions. Copyright (c) 1996-1999 EarthWeb, Inc.. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission of EarthWeb is prohibited. Please read our privacy policy for details. |